Collaborative authoring

ABSTRACT

A collaborative authoring application provides an authoring environment in which two or more users can edit a document concurrently. Each user edits a copy of the document, sends updates to a master copy of the document, and receives updates from the master copy of the document. The authoring environment generally inhibits the users from providing conflicting editing instructions to the master copy of the document. For example, each user can generate a content lock about one or more data units within the document. The authoring environment may synchronize content locks automatically and content only at the request of the user.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/539,473 (now U.S. Pat. No. 8,990,150), filed Jul. 1, 2012, entitled“Collaborative Authoring,” which application is a continuation of U.S.patent application Ser. No. 13/079,605 (now U.S. Pat. No. 8,352,418),filed Apr. 4, 2011, entitled “Client Side Locking,” which application isa continuation of U.S. patent application Ser. No. 11/938,082 (now U.S.Pat. No. 7,941,399), filed Nov. 9, 2007, entitled “CollaborativeAuthoring,” the complete disclosures of which are hereby incorporatedherein by reference.

BACKGROUND

Traditional collaborative editing tends to be performed serially. Userstake turns accessing a document, editing the document, and storing theiredits. The accessing user may place a lock on the file to inhibit otherusers from editing the document when the accessing user is editing thedocument. The iterative editing process can cause delays since each usermay wait for a turn at editing the document. In addition, the iterativeediting process may be difficult to manage. For example, each user mayneed to keep track of who is editing which portions of the document,which version of the document is the most recent, and when the user willhave a turn.

In other types of traditional collaborative editing, each user can edita different copy of a document. Subsequently, all of the edited copiesmay be merged into a single document. This large scale merge also maycause delays, lead to numerous editing conflicts, and/or be difficult tomanage. For example, the user responsible for merging the documents maybe required to track the relationship between the documents. The useralso may be responsible for resolving conflicts among two or more of theedited copies.

It is with respect to these and other considerations that the presentdisclosure has been made.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended asan aid in determining the scope of the claimed subject matter.

A collaborative authoring application provides an authoring environmentin which two or more users can edit a document concurrently. Each useredits a copy of the document, periodically sends updates to a mastercopy of the document, and periodically receives updates from the mastercopy of the document. The authoring environment generally inhibits theusers from providing conflicting editing instructions to the master copyof the document. In other embodiments, the authoring environment caninhibit editing conflicts if the users edit the document at differenttimes.

According to aspects of the disclosure, each document being authored canbe divided into one or more data units. Each user can generate a contentlock about one or more of the data units. Generating a content lockabout a data unit inhibits other users from editing the locked dataunit. In one embodiment, content locks can grow and/or shrinkautomatically as the user edits the document.

According to other aspects of the disclosure, the authoring environmentsynchronizes both content and metadata among the user copies and themaster copy of the document. In general, the authoring environmentsynchronizes metadata automatically and synchronizes content only at therequest of one of the users. In one embodiment, the metadata includescontent locks.

These and other features and advantages will be apparent from a readingof the following detailed description and a review of the associateddrawings. It is to be understood that both the foregoing generaldescription and the following detailed description are explanatory onlyand are not restrictive of aspects as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic block diagram illustrating an example authoringsystem having features that are examples of inventive aspects of thedisclosure;

FIG. 2 is a schematic block diagram illustrating the authoring system ofFIG. 1 in which a document stored on first computing device can includecontent and metadata in accordance with the principles of the presentdisclosure;

FIG. 3 is a flowchart illustrating an exemplary synchronization processby which an authoring system can synchronize a copy of a document storedon a user computing device with the master copy of the document inaccordance with the principles of the present disclosure;

FIG. 4 is a schematic block diagram of a document having five units ofdata, the second of which is locked, in accordance with the principlesof the present disclosure;

FIG. 5 is a schematic block diagram of the document of FIG. 4 in which acontent lock has been added to the third data unit in accordance withthe principles of the present disclosure;

FIG. 6 is a schematic block diagram of the document of FIG. 4 in whichthe content locks on the second and third data units have been releasedand a new content lock has been added to the fifth data unit inaccordance with the principles of the present disclosure;

FIG. 7 is a schematic block diagram of a lock table in accordance withthe principles of the present disclosure;

FIG. 8 is a flowchart illustrating an example synchronization processesimplemented by an authoring application to share updates made by a userof the authoring application with other users in accordance with theprinciples of the present disclosure;

FIG. 9 is a flowchart illustrating another example synchronizationprocess implemented by an authoring application to instantiate updatesmade by other users into the document being edited with the authoringapplication in accordance with the principles of the present disclosure;

FIG. 10 is a schematic block diagram of an authoring environmentincluding a first computing device on which a master copy of a documentto be authored is to be stored in accordance with the principles of thepresent disclosure;

FIG. 11 is a schematic block diagram of a user computing systemconfigured to implement an authoring environment in accordance with theprinciples of the present disclosure;

FIG. 12 is a schematic block diagram of an authoring system illustratinga synchronization cycle implemented by the authoring application on theuser computing device in accordance with the principles of the presentdisclosure;

FIG. 13 is a flowchart illustrating an operational flow for anotherexemplary synchronization process by which a user computing system cansend and receive updates while editing a document in accordance with theprinciples of the present disclosure;

FIGS. 14-26 are schematic block diagrams of the caches stored on a firstcomputing device, a first user computing device, and a second usercomputing device at different points in time during a collaborativeauthoring session in which a first user and a second user of the firstand second user computing devices edit a document concurrently inaccordance with the principles of the present disclosure; and

FIGS. 27-31 illustrate changes to an exemplary user interface of a firstauthoring application as a first user and a second user collaborativelyauthor a document in accordance with the principles of the presentdisclosure.

DETAILED DESCRIPTION

In the following detailed description, references are made to theaccompanying drawings that form a part hereof, and in which are shown byway of illustrations specific embodiments or examples. While thedisclosure will be described in the general context of program modulesthat execute in conjunction with an application program that runs on anoperating system on a computer system, those skilled in the art willrecognize that the disclosure also may be implemented in combinationwith other program modules. The embodiments described herein may becombined and other embodiments may be utilized without departing fromthe spirit or scope of the present disclosure. The following detaileddescription is therefore not to be taken in a limiting sense, and thescope of the invention is defined by the appended claims and theirequivalents.

Embodiments of the present disclosure provide an environment in whichmultiple users can collaboratively author a document. FIG. 1 illustratesan example authoring system 100 having features that are examples ofinventive aspects of the disclosure. The authoring system 100 includes astorage device 120 storing a master copy of a document 150. In oneembodiment, the storage device 120 can include a computing device. Inanother embodiment, the storage device 120 can include one or morestorage devices (e.g., a network of computing devices).

The authoring system 100 also includes at least one user computingdevice 110 that is communicatively coupled to the storage device 120.Each of the user computing devices 110 can edit the document 150 bycreating a user copy 155 of the document 150 and editing the user copy155. The user copies 155 of the document 150 are synchronized when theuser computing devices 110 periodically send to the storage device 120updates to be shared with the other user computing devices andperiodically obtain from the storage device 120 updates from other usercomputing devices.

As the term is used herein, a user computing device 110 includes anycomputing device that obtains a user copy of a document to be authoredfrom a master copy of the document. The user computing device 110 can bedifferent from the storage device 120 or can include a different useraccount implemented on the storage device 120. In one embodiment, acomputing device that acts as a storage device 120 for one document mayact as a user computing device 110 for a different document and viceversa.

In the example shown, four user computing devices 110A, 110B, 110C, and110D are communicatively coupled to the storage device 120. In otherembodiments, however, any number of computing devices 110 may be coupledto the storage device 120. In the example shown, each user computingdevice 110A, 110B, 110C, 110D can send to the storage device 120 updatesgenerated by the user of the user computing device and can request fromthe storage device 120 updates generated by the users of the other usercomputing devices. In one embodiment, the storage device 120 can be aserver computing device and the user computing devices 110A, 110B, 110C,110D can be client computing devices.

As shown in FIG. 2, the document 150 stored on the storage device 120can include content 152 and metadata 154. Authoring applications 130 onthe user computing devices 110 process and manipulate the content andmetadata of the user copies 155 of the document 150. In someembodiments, metadata 154 can be stored separately from content 152. Forexample, content 152 can be stored in the document 150 and metadata 154can be stored in a table (see FIG. 7) separate from the document 150. Inother embodiments, however, the metadata 154 can be stored within thedocument 150.

In general, the user computing devices 110 can synchronize updates tothe content 152 separately from updates to the metadata 154. In general,metadata updates 154 are automatically synchronized among the storagedevice 120 and user computing devices 110, whereas content updates 152from each user computing device 110 are synchronized at the request ofthe respective user.

FIG. 3 is a flowchart illustrating an exemplary synchronization process300 by which an authoring system 100 can synchronize a copy 155 of adocument stored on a user computing device 110 with the master copy 150of the document stored on the storage device 120. The synchronizationprocess 300 initializes and begins at a start module 302 and proceeds toa first update operation 304.

The first update operation 304 synchronizes the metadata of the copy 155with the metadata of the document 150 without requiring any interactionwith the user. For example, the first update operation 304 can providean exchange of metadata between the storage device 120 and the usercomputing device 110 at periodic time intervals. In one embodiment, thefirst update operation 304 provides for an exchange of metadata everyfew seconds. In other embodiments, however, the first update operation304 can provide for the exchange of metadata to occur in shorter orlonger time intervals.

A request module 306 determines whether a request to synchronize contenthas been received. For example, the request module 306 can determinewhether a user of one of the user computing devices 110 has requested toshare content changes with other users. In another embodiment, therequest module 306 can determine whether a user of one of the usercomputing devices 110 has requested to view content changes made byother users.

If the request module 306 determines that no request to synchronizecontent has been made, then the synchronization process 300 cycles backto the first update operation 304 and begins again. If the requestmodule 306, however, determines that a request to synchronize contenthas been received, then the synchronization process 300 proceeds to asecond update operation 308, which provides an exchange of contentbetween the storage device 120 and the user computing device 110. Thesynchronization process 300 completes and ends at a stop module 310.

As the term is used herein, content updates 152 refer to any addition,deletion, and/or revision made to the substantive content of a document.For example, content updates for a word processing document can includeadded paragraphs (i.e., or sections thereof), deleted paragraphs (i.e.,or section thereof), and/or revised paragraphs (i.e., or sectionsthereof). In another embodiment, content updates for a presentationdocument can include added, deleted, and/or revised pictures, text,animations, sounds, and other such data objects.

As the term is used herein, metadata updates 154 refer to any addition,deletion, and/or revision made to metadata of the document. Non-limitingexamples of document metadata include content locks, presenceinformation, and other such data. As will be discussed herein, contentlocks inhibit editing of content within the lock by users that do notown the lock. Presence information indicates which users have indicatedan intention to edit the document as will be discussed in greater detailherein.

Referring to FIGS. 4-9, content locks inhibit editing conflicts byindicating which portions of a document have been claimed by anotheruser. In some embodiments, the content locks can prevent (i.e., bar) auser from editing a portion of a document that has been claimed byanother user. In other embodiments, however, the user can choose tobreak the content lock and edit the portion of the document. In suchcases, the lock can warn the user that conflicts may arise when editingthe locked section.

For example, FIG. 4 is a schematic block diagram of a document 400having five units of data 410, 420, 430, 440, 450. In one embodiment,the document 400 is a word processing document and the units of data410-450 are paragraphs of text. In another embodiment, the document 400is a presentation document and the first unit of data 410 is a title orsubject heading, the second unit of data 420 is a picture or other dataobject, and the remaining units of data 430, 440, 450 are blocks oftext.

A first user can generate a lock about one or more of the units of data410-450 of the document 400. In the example shown in FIG. 4, the secondunit of data 420 has been locked by the first user, as indicated by thecross-hatching. By generating the content lock, the first user hasindicated the first user intends to edit the unit of data 420. Forexample, the user can generate the lock when the user is activelyediting the unit of data 420. In another embodiment, the user cangenerate the lock and then edit the unit of data 420 at a later time. Asnoted above, the authoring application managing the document 400 mayprevent a user other than the first user from editing the locked dataunit 420.

In general, a content lock generated by a first user is displayed to allother users who access the document during the life of the lock. In oneembodiment, the first user also can view the content lock. Locks can bedisplayed using different types of indicia. For example, in oneembodiment, the background of a locked unit of data may be colored,shaded, or patterned (e.g., see data unit 420 of FIG. 4). In anotherembodiment, the content (e.g., text, picture, shape, or other dataobject) of the locked unit may be colored, shaded, or patterned. In yetanother embodiment, a box, bracket, or symbol can be displayed adjacentthe locked unit of data to indicate the lock.

A content lock may be generated around one or more units of data withina document. In some embodiments, the content lock can be generatedimplicitly without express instruction from the user. For example, anauthoring application may generate a content lock about a data unit whena user positions a cursor within, highlights, or otherwise selects thedata unit. In another embodiment, an authoring application may generatea content lock about a data unit when the user begins editing the dataunit. In another embodiment, an authoring application may generate acontent lock about a data unit when a user saves edits made to the dataunit. In some embodiments, the authoring application may generatecontent locks around multiple, inter-dependent data units within thedocument even if only one of the data units is claimed by a user. Inother embodiments, a user may explicitly define a content lock about oneor more data units.

In some embodiments, a content lock can grow to include additional unitsof data within the document and/or shrink to release one or more unitsof data within the document. In one embodiment, the content lock cangrow to include only contiguous units of data. For example, as shown inFIG. 5, the content lock (e.g., see cross-hatching) around the seconddata unit 420 can expand to include the third data unit 430 if the userselects or edits the third data unit 430. A content lock or portionthereof generally can be released at the discretion of the user whogenerated the content lock. In some embodiments, the user who generatedthe content lock releases the content lock by selecting or editinganother data unit.

In one embodiment, the user must indicate the user has finished editingthe data unit before the authoring application will release the lock.For example, the authoring application may release the lock only afterthe user has provided instructions to store the document. In anotherembodiment, the authoring application may release a lock after the userselects or begins editing a remote data unit, such as the fifth dataunit 450 of FIG. 6. In another embodiment, the authoring applicationonly releases a lock after both movement to a non-contiguous data unitand a finalization act (e.g., instructions to store the document). Inother embodiments, a content lock can be released explicitly by anadministrator or another user.

Referring to FIG. 7, lock metadata can be stored in a variety ofdifferent formats. For example, the lock metadata of FIG. 7 is stored ina table format 500. The lock table 500 of FIG. 7 includes a list ofusers, each of whom is identified with a user identifier (e.g., anidentification number) that is uniquely assigned to the user. Data unitsto be locked are identified with unit identifiers (e.g., identificationnumbers) that are uniquely assigned to each data unit within a document.The lock table 500 associates the unit identifiers of the one or moredata units to be locked with the user identifiers of the users who ownthe locks.

For example, in the lock table 500, data units 512 and 514 areassociated with a first user 510. Other users, therefore, are inhibitedfrom editing data units 512 and 514. Data unit 522 is associated withuser 520. Other users, including the first user 510, therefore, areinhibited from editing data unit 522. The fourth user 540 has not lockedany portion of the document and so is not associated with any unitidentifiers. In other embodiments, however, lock metadata can be storedin a different format or within the document. For example, the locktable 500 can be arranged by unit identifier instead of by useridentifier.

Presence metadata also can be stored in a variety of formats. Forexample, presence metadata can be stored in the lock table 500 of FIG.7. In another embodiment, however, presence metadata can be stored in aseparate table or in a different format. Presence metadata includes theuser identifier of each user that is currently accessing the document orthat has staked a claim (e.g., generated a content lock) on a data unitof the document. For example, a metadata table, such as the lock table500, can store the user identifier of each user having a claim to atleast one data unit of the document. Like lock metadata, presencemetadata can be synchronized automatically.

FIGS. 8 and 9 are flowcharts illustrating example synchronizationprocesses 600, 700 by which content and locks can be synchronized amongmultiple computing devices. The first synchronization process 600 isimplemented by an authoring application to share with other usersupdates made by a first user with the authoring application. The secondsynchronization process 700 is implemented by an authoring applicationto instantiate updates made by other users into the document beingedited with the authoring application.

The first synchronization process 600 of FIG. 8 initializes and beginsat a start module 602 and proceeds to a receive operation 604. Thereceive operation 604 receives an instruction from the first user toperform an editing operation on one or more data units within adocument. Non-limiting examples of editing operations include adding,editing, and/or deleting data units (e.g., text, drawings, pictures,shapes, headings, etc.) or portions thereof, adding and/or deletingformatting of the data units, rearranging a sequence of the data units,and other such operations.

A first determination module 606 checks if the data unit on which theediting operation is to be performed is locked. For example, the firstdetermination module 606 can access a lock table, such as the lock table500 of FIG. 7, to determine whether a unit identifier assigned to thedata unit is associated with any user. In another embodiment, the firstdetermination module 606 can otherwise determine whether the data unitis locked.

If the first determination module 606 determines the data unit is notlocked, then a generate operation 608 creates a content lock on the dataunit. For example, in one embodiment, the generate operation 608 can addan entry to the lock table 500 of FIG. 7 associating the unit identifierof the data unit with the user identifier of the first user. A transmitoperation 610 sends lock metadata indicating the existence of the newlygenerated lock to the device storing the master copy of the document.For example, the transmit operation 610 can send the lock metadata froma user computing device, such as computing device 110A of FIG. 1, to astorage device, such as storage device 120. In one embodiment, the lockmetadata includes instructions that describe incremental edits (e.g.,delta states) to the lock metadata. An implement operation 614 performsthe editing operation on the data unit.

Alternatively, if the first determination module 606 determines the dataunit is locked, then a second determination module 612 obtains ownershipinformation for the lock. In one embodiment, if the second determinationmodule 612 determines the lock is owned by another user, then thesynchronization process 600 completes and ends at a stop module 620without performing the editing operation. In another embodiment (notshown), the synchronization process 600 may enable the first user tochoose to break the lock and then proceed to generate operation 608.However, if the second determination module 612 determines the lock isowned by the first user, then the synchronization process 600 proceedsto the implement operation 614 discussed above. In another embodiment(not shown), the synchronization process 600 can determine whether thelock on any data units should be released.

A third determination operation 616 determines whether the first userhas provided an instruction (either explicitly or implicitly) to sharecontent changes to the data unit resulting from implementing the editingoperation. For example, the third determination operation 616 maydetermine whether the first user has provided an instruction to storethe document. In another embodiment, the third determination operation616 may determine whether the first user has selected a “share changes”button or other such indicia. In another embodiment, the thirddetermination operation 616 may determine an auto-save feature has beenimplemented by the application. If the third determination operation 616determines instructions to share have not been provided, then thesynchronization process 600 cycles back to the receive operation 604 andbegins again.

If the determination operation 616 determines instructions to share havebeen provided, however, then the synchronization process 600 proceeds toa transmit operation 618, which sends content updates to the devicestoring the master copy of the document. Content updates indicatechanges made to the content of the document by the editing operation.For example, the transmit operation 618 can send the content updatesfrom a user computing device 110A of FIG. 1 to a storage device 120. Inone embodiment, content updates include a newly generated version of thedocument. In another embodiment, content updates indicate incrementaledits (e.g., delta states) to the content between the current user copyof the document and the master copy of the document. The synchronizationprocess 600 completes and ends at the stop module 620 as discussedabove.

The second synchronization process 700 of FIG. 9 initializes and beginsat a start module 702 and proceeds to a receive operation 704. Thereceive operation 704 receives an update based on changes made to thedocument by other users. The update can include changes to the contentand/or metadata of the document. In one embodiment, the receiveoperation 704 can poll the device storing the master copy of thedocument and request updates. In another embodiment, the device storingthe master copy can push changes to the authoring application.

A first determination module 706 determines whether the update includesany changes to the metadata of the document. For example, the firstdetermination module 706 can determine whether any other user hasestablished a new lock or released a lock on a data unit. In anotherembodiment, the first determination module 706 can determine whetheranother user has accessed the document.

If the first determination module 706 determines a metadata update hasbeen received, then an implement operation 708 automaticallyinstantiates the received metadata updates. For example, the implementoperation 708 can cause the authoring application to update a locktable, such as lock table 500 of FIG. 7, based on the metadata update.However, if the first determination module 706 determines no metadataupdate has been received, then the second synchronization process 700proceeds to a second determination module 710.

The second determination module 710 determines whether the updateincludes any changes to the content of the document. For example, thesecond determination module 710 can determine whether any data unitshave been added, deleted, revised, or moved. If the second determinationmodule 710 determines a content update has not been received, then thesecond synchronization process 700 cycles back to the receive operation704 to begin again. However, if the second determination module 710determines a content update has been received, then the secondsynchronization process 700 proceeds to an indicate operation 712.

The indicate operation 712 alerts the first user that a content updateis available for viewing. For example, the indicate operation 712 candisplay a graphic, text box, numerical indicia, or other messageindicating the availability of the content update. In one embodiment,the indicate operation 712 provides information to the user indicatinghow many updates are available. Other information about the updates(e.g., user who made the updates, timestamp, etc.) also may beindicated.

A third determination module 714 determines whether the authoringapplication has received instructions from the first user (eitherexplicitly or implicitly) to view and/or instantiate the contentupdates. For example, the third determination module 714 can determinewhether the user has selected a view option (e.g., via a button, menu,or other interface tool) of the authoring application. In anotherembodiment, the third determination module 714 may determine the userhas selected an auto-instantiate option. If the third determinationmodule 714 determines the authoring application has not received suchinstructions from the first user, then the second synchronizationprocess 700 cycles back to the receive operation 704 and begins again.

If the third determination module 714 determines the authoringapplication has received instructions from the first user, then aninstantiate operation 716 displays the content updates to the firstuser. For example, in one embodiment, the instantiate operation 716 canmerge the available content updates into the first user's copy of thedocument. In another embodiment, the instantiate operation 716 canannotate the first user's copy of the document to indicate which contenthas changed. Additional annotations can indicate which users made whichchanges. In one embodiment, the instantiate operation 716 performsconflict resolution between the user copy and the updates. The secondsynchronization process 700 completes and ends at a stop module 718.

FIGS. 10-12 provide greater detail in how synchronization between theuser copy and the master copy of the document is implemented by a usercomputing device. FIG. 10 is a schematic block diagram of an authoringsystem 800 including a storage device 820 on which a master copy of adocument to be authored is to be stored. The authoring system 800 alsoincludes at least one user computing device 810 communicatively coupledto the storage device 820.

The user computing device 810 includes an authoring application 812configured to provide an authoring environment in which a user cancreate and/or manipulate a document to be authored. The user computingdevice 810 also includes a cache 814, a layer object (“LO”) 816, and asynchronization manager (“sync manager”) 818. The cache 814 stores auser copy of the document to be authored. The cache 814 also stores themetadata, including lock and presence metadata, associated with thedocument. Updates to the content and metadata of the document also canbe stored in the cache 814.

The layer object 816 provides an interface between the authoringapplication 812 and the cache 814. The layer object 816 also provides aninterface between the authoring application 812 and the sync manager818. The sync manager 818 communicates with the storage device 820 andprovides an interface between the storage device 820 and the cache 814.For example, the sync manager 818 can send updates to and obtain updatesfrom the storage device 820 and the cache 814.

In general, an authoring environment having features that are examplesof inventive aspects in accordance with the principles of the disclosurecan be implemented on a user computing device (e.g., a personalcomputer, a server computer, a notebook computer, a PDA, a Smartphone,or any other such computing device). A non-limiting embodiment of a usercomputing system 900 configured to implement an authoring environment isdescribed herein with reference to FIG. 11.

In FIG. 11, the exemplary computing system 900 for implementing theprinciples of the disclosure includes a user computing device, such asuser computing device 910. In a basic configuration, the user computingdevice 910 typically includes at least one processing unit 915 forexecuting applications and programs stored in system memory 920.Depending on the exact configuration and type of computing device 910,the system memory 920 may include, but is not limited to, RAM, ROM,EEPROM, flash memory, CD-ROM, digital versatile disks (DVD) or otheroptical storage devices, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or other memorytechnology.

System memory 920 typically stores an operating system 922, such as theWINDOWS® operating systems from MICROSOFT CORPORATION of Redmond, Wash.,suitable for controlling the operation of the computing device 910.System memory 920 also may include a document cache 926 in which a usercopy 927 of a document can be stored. Metadata 929 of the document alsocan be stored within the user cache 926.

The system memory 920 also may store one or more software applications,such as authoring applications 924 for creating and editing documents.One non-limiting example of an authoring application 924 suitable forauthoring documents in accordance with the principles of the presentdisclosure is MICROSOFT® OFFICE WORD authoring software from MICROSOFTCORPORATION of Redmond, Wash. Other non-limiting examples of authoringapplications include POWERPOINT® presentation software and VISIO®drawing and diagramming software, both also from MICROSOFT CORPORATIONof Redmond, Wash.

Computing device 910 also may have input device(s) 930, such as akeyboard, mouse, pen, voice input device, touch input device, etc., forentering and manipulating data. Output device(s) 935, such as a displayscreen, speakers, printer, etc., also may be included. These outputdevices 935 are well known in the art and need not be discussed atlength herein.

The computing device 910 also may contain communication connections 940that allow the device 910 to communicate with other computing devices,for example, the storage device 820 of FIG. 10, over a network in adistributed computing environment (e.g., an intranet or the Internet).By way of example, and not limitation, communication device media 940includes wired media such as a wired network or direct-wired connection,and wireless media, such as acoustic, RF, infrared and other wirelessmedia.

FIG. 12 is a schematic block diagram of an authoring system 1000illustrating the synchronization cycle implemented by the authoringapplication on the user computing device. The authoring system 1000includes a storage device 1020 on which the document to be authored isto be stored and a user computing device 1010. The user computing device1010 includes an authoring application 1012, a cache 1014, a layerobject 1016, and a sync manager 1018. The cache 1014 of the usercomputing device 1010 is configured to store a base copy 1013 of thedocument to be authored, a working copy 1015, an upload copy 1017, and adownload copy 1019. The cache 1014 also is configured to store metadata1011 of the document.

FIG. 13 is a flowchart illustrating an operational flow for an exemplarysynchronization process 1100 by which a user computing system, such asuser computing device 1010, can send and receive updates while authoringa document. The synchronization process 1100 initializes and begins at astart module 1102 and proceeds to an obtain operation 1104. The obtainoperation 1104 causes the sync manager 1018 of the user computing device1010 to obtain from the storage device 1020 a download copy 1017 of thedocument to be authored. The download copy 1017 of the document reflectsthe state of the master copy of the document at the time the document isobtained from the storage device 1020. For example, the obtain operation1104 can cause the sync manager 1018 to pull from the storage device1020 a copy of the most recent version of the master copy of thedocument.

A generate operation 1106 creates a base copy 1013 and a working copy1015 of the document based on the download copy 1017. The working copy1015 of the document can be manipulated by the authoring application1012 to allow the user to edit the document. Accordingly, the workingcopy 1015 reflects the current state of the document as edited by theuser of the authoring application 1012. The base copy 1013 reflects thestate of the document at the time just before the user begins editingthe document. In one embodiment, the layer object 1016 generates thebase copy 1013 of the document and the working copy 1015 and providesthe working copy 1015 to the authoring application 1012.

To obtain content updates generated by other users, a poll operation1108 causes the sync manager 1018 to contact the storage device 1020periodically to obtain an updated download copy 1017 of the documentbeing authored. The download copy 1017 reflects the state of the mastercopy of the document at the time of download. The master copy is storedon storage device 1020 and may include changes made by other users sincethe base copy 1013 was generated. The sync manager 1018 stores anyupdated download copy 1017 of the document in the cache 1014.

An edit operation 1110 receives any instructions provided by the user tothe authoring application 1012 to perform an editing operation on thedocument. The application 1012 makes the edits to the working copy ofthe document 1015. The authoring application 1012 also makes metadatachanges as appropriate when implementing the editing operations.

At a first determination module 1112, the layer object 1016 checks thecache 1014 to determine whether any updates have been received duringthe poll operation 1108 (i.e., whether an updated download copy 1017 isavailable in the cache 1014). In one embodiment, the first determinationmodule 1112 is performed at periodic intervals regardless of whether theuser has edited the working copy of the document. In differentembodiments, the first determination module 1112 can be performed, e.g.,every few seconds, milliseconds, or minutes.

If the layer object 1016 determines a new download copy 1017 is notavailable, then the synchronization process 1100 proceeds to a seconddetermination module 1116, which will be discussed in greater detailbelow. If the layer object 1016 determines a new download copy 1017 isavailable, however, then the synchronization process 1100 proceeds to async operation 1114. In one embodiment, the sync operation 1114automatically instantiates any metadata updates found in the downloadcopy 1017 without requiring any interaction with the user of theauthoring application 1012. For example, the layer object 1016 mayautomatically instantiates any lock metadata reflected in the downloadcopy 1017 into the working copy 1015 of the document.

In some embodiments, the sync operation 1114 does not automaticallyinstantiate any content updates from the download copy 1017 into theworking copy 1015. Rather, the sync operation 1114 only instantiatescontent updates when the user of the authoring application 1012 providesinstructions to integrate the content updates. In other embodiments,however, the sync operation 1114 automatically instantiates the contentupdates. In one embodiment, the sync operation 1114 causes the layerobject 1016 to merge the updated download copy 1017 with the workingcopy 1015 when instructions to integrate are provided. In oneembodiment, the sync operation 1114 is the same as the secondsynchronization process 700 shown in FIG. 9. In other embodiments,however, other synchronization processes can be used to integrate theupdates with the working copy 1015 of the document. The synchronizationprocess 1100 proceeds from the sync operation 1114 to the seconddetermination module 1116.

The second determination module 1116 determines whether the user madeany changes to the working copy 1015 of the document or to the metadata1011 of the document during the edit operation 1110. If the seconddetermination module 1116 determines that no edits (i.e., neithercontent nor metadata) have been made, then the synchronization process1100 cycles back to the poll operation 1108 and begins again. If thesecond determination module 1116 determines the user has made contentedits (e.g., revising a data unit of the document) and/or metadata edits(e.g., locking a data unit of the document), however, then a shareoperation 1118 synchronizes the edits with the storage device 1020.

The share operation 1118 causes the sync manager 1018 of the usercomputing device 1010 to send automatically to the storage device 1020any changes to the metadata of the document without requiring anyinteraction from the user of the authoring application 1012. In oneembodiment, the share operation 1118 does not cause the sync manager1018 to send content updates to the storage device 1020 automatically.Rather, the sync manager 1018 only sends content updates to the storagedevice 1020 when instructed to do so by the layer object 1016.Automatically pushing only metadata may enhance the user experience byincreasing update efficiency, reduce network bandwidth usage, andprovide conflict inhibition without requiring auto-syncing of content.In other embodiments, however, the share operation 1118 automaticallypushes content as well as metadata. In one embodiment, the shareoperation 1118 is the same as the first synchronization process 600 ofFIG. 8. In other embodiments, however, other synchronization processescan be utilized.

For example, when the user wishes to share content revisions made by theuser, the user will instruct the authoring application 1012 to submitthe revisions to the storage device 1020 for integration with the mastercopy of the document. In one embodiment, the authoring application 1012will instruct the layer object 1016 to generate an upload copy 1019 ofthe document. Generally, the layer object 1016 generates the upload copy1019 based on the working copy 1015. The sync manager 1018 attempts topush the upload copy 1019 to the storage device 1020. Thesynchronization process 1100 completes and ends at a stop module 1120.

In some embodiments, the share operation 1118 cannot send contentupdates to the storage device 1020 until all previous content updatesreceived from the storage device 1020 have been instantiated into theworking copy 1015 of the document. In such embodiments, the upload copy1019 can be generated by merging the working copy 1015 of the documentwith the most recently obtained download copy 1017. In one embodiment,the sync manager 1018 polls the storage device 1020 for an updateddownload copy 1017 when the layer object 1016 attempts to generate anupload copy 1019.

If the sync manger 1018 fails to push the upload copy 1019 to thestorage device 1020 (e.g., if the upload copy 1019 does not reflect themost recent changes instantiated into the master copy), then the syncmanager 1018 retry with a revised update document 1019. For example, thesync manager 1018 may obtain a new download copy 1017 from the storagedevice 1020 and the layer object 1016 may generate a new upload copyfrom the working copy and the new download copy 1017. In one embodiment,the sync manager 1018 will continue to revise and push an upload copy1019 to the storage device 1020 until successful.

Referring to FIGS. 14-31, the principles of the present disclosure canbe better understood by walking through some example applications. FIGS.14-26 represent changes made to a cache of a storage device, a cache1214 a first user computing device, and a cache 1234 of a second usercomputing device during a collaborative authoring session in which afirst user and a second user edit a document concurrently. In otherembodiments, however, the first and second users can edit the documentat different times using the same processes.

In FIG. 14, the first user has created a document and saved an initialdraft of the document to a storage device as a master copy 1250.Alternatively, the first user may have accessed the master copy 1250 ofan existing document. The second user has not yet accessed the document.

The master copy 1250 of the document has a corresponding master locktable. For the sake of convenience, in the example shown in FIGS. 14-26,the master lock table is displayed as part of the master copy 1250. Inother embodiments, however, the master lock table can be storedseparately from the master copy 1250 of the document. Similarly, forease in understanding, locks associated with each copy of the document(e.g., base copy, working copy, download copy, and upload copy) storedon a user cache 1214, 1234 are shown in FIGS. 14-26 as part of the copy.In other embodiments, however, metadata may be separately stored foreach document copy or for each user.

The master copy 1250 of the document includes a first data unitcontaining the text “Hello World” and a lock E1 on the first data unit.The lock E1 is owned by (i.e., assigned to) the first user. The contentand metadata of the master copy 1250 are reflected in the base copy anddownload copy stored in the cache 1214 of the first user. Because thefirst user sent the initial draft of the document to the storage device,the upload copy stored in the cache 1214 also reflects the content andmetadata of the master copy 1250.

Since sending the initial draft to the storage device, the first userhas edited the working copy of the document to include a second dataunit containing the text “Testing.” A second lock E2 has been addedabout the second data unit. In one embodiment, the second lock E2 is anew lock assigned to the user. In another embodiment, the second lock E2is an extension of the first lock E1. For example, a new unit identifiercan be assigned to the first user in a metadata table stored in thecache 1214 of the first user. In one embodiment, the first user createsthe second lock E2 by moving a cursor to start a new data unit (e.g.,paragraph) and typing “Testing.” The first lock E1 is not yet releasedbecause the first user has not yet indicated editing on the first dataunit is final (e.g., by saving after moving the cursor).

In FIG. 15, the second user accesses the master copy 1250 of thedocument stored on the storage device. The second user obtains adownload copy of the document and stores the download copy into thecache 1234 of the second user. The download copy includes the contentand metadata of the master copy 1250. The download copy does not includethe most recent content and metadata contained in the working copy ofthe first user. The layer object of the second user generates a basecopy and a working copy of the document based on the download copy. Theauthoring application utilized by the second user displays the contentand any locks of the working copy to the second user.

In some embodiments, the second user can edit the document even before acoauthoring session has been fully established (i.e., before the firstand second user computing devices learn of the presence of the other).For example, the second user is allowed to edit the second working copyof the document while the first and second user computing devicesexchange greetings (i.e., handshake). Typically, metadata is notexchanged automatically before the first and second computing deviceslearn of the existence of one another.

In FIG. 16, the first and second computing devices each have discoveredthe existence of the other. Accordingly, each of the first and secondcomputing devices has begun transmitting metadata updates automaticallyto each other. As shown in FIG. 16, the first authoring applicationprovides updated lock metadata (e.g., the second lock) from the locktable of the first user to the storage device 1220 (e.g., via a layerobject and sync manager). The authoring application does not provideupdated content information to the storage device 1220, however, becauseno instructions to share content updates have been received from thefirst user.

In FIG. 17, the storage device has integrated the updated lock metadata(e.g., the second lock E2) into the master metadata table of the mastercopy 1250. The lock metadata has not yet been obtained by the seconduser computing device. In FIG. 18, the second user computing device haspolled the storage device and obtained a new download copy of the mastercopy 1250. A new download copy also has been generated (e.g., via alayer object) on the first cache 1214 based on the upload copy. Inanother embodiment, the first user computing device also may have polledthe storage device and obtained a new download copy of the master copy1250. Both of the new download copies reflect the updated lockinformation (e.g., lock E2) from the working copy of the first user.

In FIG. 19, the second computing device generates (e.g., via a layerobject) a new working copy based on the new download copy. Accordingly,the new working copy of the second computing device contains the secondlock E2 on the second data unit. The new working copy does not includethe second data unit itself, however. In one embodiment, the workingcopy of the second user computing device displays a blank/empty dataunit and indicates that the blank/empty data unit is locked. In anotherembodiment, the working copy does not display the second data unit atall and the lock E2 is not indicated to the second user until the seconddata unit is visible to the second user.

In FIG. 20, the second user adds a third data unit to the document and athird lock E3 around the third data unit (e.g., in the memory of theauthoring application). The third data unit contains the text “GoodbyeWorld”. The second authoring application generates (e.g., via a layerobject) a working copy of the document including the third data unit andthe third lock E3. The second authoring application also automaticallyprovides (e.g., via a sync manager) the third lock E3 to the storagedevice. However, the second authoring application does not provide thethird data unit to the storage device.

Also in FIG. 20, the first user releases the first lock E1 after thefirst user indicates the first user has finished editing the first dataunit. For example, the first user can provide instructions to store thedocument when the cursor of the first user is positioned within thesecond data unit. In one embodiment, the second data unit may be locatedremote from the first data unit. In the example shown, the finalizationindication provided by the first user does not indicate the first userwishes to share content changes made by the first user. Accordingly, thefirst authoring application does not generate (e.g., via a layer object)an upload copy containing content changes for distribution to thestorage device.

In FIG. 21, the third lock E3 has been stored in the master lock tableof the master copy 1250 of the document on the storage device. The firstuser computing device subsequently polls (e.g., via a sync manager) thestorage device to check for updates. The first user computing deviceobtained (e.g., via a sync manager) a new download copy of the documentfrom the storage device based on the master copy 1250. The new downloadcopy contains the third lock E3. The first authoring applicationautomatically instantiates (e.g., via a layer object) the third lock E3into the working copy of the first authoring application. As notedabove, the third lock E3 optionally may be displayed to the first userusing the user interface of the first authoring application.

In FIG. 22, the second user releases the third lock E3 when the seconduser indicates the second user has finished editing the third data unit.The third lock E3 is removed from the metadata table of the second user.In the example block diagram shown in FIG. 22, the third lock E3 isremoved from the metadata tables corresponding to the working copy ofthe second authoring application.

In the example shown in FIG. 22, the finalization indication provided bythe second user indicates the second user wishes to share contentchanges with other users. For example, the second user may remove acursor from the third data unit and then provide instructions to storethe document. Accordingly, the second authoring application may generatean upload copy containing the content changes based on the working copy.In one embodiment, the upload copy also can be based on any contentupdates (e.g., in this case none) found in the download copy that hadnot yet been instantiated into the working copy. In the example shown,the upload copy includes the third data unit including the phrase“Goodbye World.”

In FIG. 23, the storage device obtains the third data unit from theupload copy of the second user computing device and merges the thirddata unit into the master copy 1250 of the storage device. The locktable associated with the master copy 1250 indicates the third lock E3has been released. As shown in FIG. 24, upon a successful push to thestorage device, the second authoring application copies (e.g., via alayer object) the upload copy to the download copy and the base copy ofthe second cache 1234.

In FIG. 25, the first user computing device obtains (e.g., via a syncmanager) a new download copy of the master copy 1250 of the document.The first authoring application determines (e.g., via a layer object)the new download copy has been obtained and determines the new downloadcopy includes content changes. The authoring application automaticallymerges any new locks (none in this case) into the working copy of thecache 1214. The user interface of the first authoring application mayindicate content updates are available for viewing.

In FIG. 26, the first user chooses to instantiate the content updatesavailable in the cache 1214 into the working copy of the document.Accordingly, the authoring application merges the download copy storedin the cache 1214 with the working copy of the first authoringapplication. The third data unit is added to the working copy of thefirst authoring application and is displayed to the first user. Thethird lock E3 is released in the metadata table associated with theworking copy of the first authoring application. The first user,therefore, may instruct the first authoring application to edit thethird data unit.

Referring now to FIGS. 27-31, the user experience during the coauthoringsession is described in detail below. FIGS. 27-31 illustrate changes toan exemplary user interface 2000 of a first authoring application as afirst user and a second user collaboratively author a document 2010. Thefirst user, Jane Doe, edits the document 2010 using the first authoringapplication and the second user, John Doe, edits the document 2010 usinga different authoring application.

The document 2010 includes a first data unit 2012, a second data unit2014, a third data unit 2016, and a fourth data unit 2018. The firstuser places a content lock 2022 around the first data unit 2012. Forexample, in one embodiment, the first user may move her cursor 2015 tothe first data unit 2012. In another embodiment, the first user mayprovide instructions to perform one or more editing operations on thefirst data unit 2012.

In FIG. 28, the first user has added text to the first data unit 2012.The lock on the first data unit inhibits the second user from editingthe first data unit 2012. In one embodiment, the first lock 2022prevents the second user from editing the first data unit 2012. Inanother embodiment, the first lock 2022 warns the second user againstediting the first data unit 2012, but does not bar editing by the seconduser. In yet another embodiment, the first lock 2022 merely indicatesthe first user has expressed an intention to edit the first data unit2012.

In FIG. 29, the second user has placed a content lock 2024 about thethird data unit 2016. Because the second user has chosen to not sharehis changes, the second lock may be visible on the user interface 2000of the first authoring application, but any changes made to the thirddata unit 2016 by the second user are not visible yet. In the exampleshown, the second lock 2024 is indicated by the user interface 2000 bydisplaying a bracket indicating the scope of the second lock 2024. Thesecond lock 2024 also can include a nametag indicating the owner of thesecond lock 2024. In FIG. 29, the nametag includes text identifying thesecond user and an icon. The icon can further identify a user by color,symbol, or other graphic.

In FIG. 30, the first authoring application receives content updates forthe document 2010. The second user has chosen to share content changeswith other users and accordingly merged content updates into a mastercopy of the document 2010 (e.g., via one of the synchronizationprocesses described above). A sync manager of the first authoringapplication obtained the updates from the master copy of the document2010 by polling the device storing the master copy.

The user interface 2000 of the first authoring application displays analert 2030 to the first user indicating the availability of the contentupdate. In the example shown, a text box 2030 appears in the userinterface 2000. In another embodiment, the second lock or text withinthe second lock can change color, pattern, or formatting. In anotherembodiment, an update counter increments when each new update isavailable.

The first user can choose to view/instantiate the changes made by thesecond user or to ignore the content updates. The first user cancontinue to edit any unlocked data units within the document 2010 whileignoring the content updates. In one embodiment, the first user mustinstantiate the content updates before merging her updates with themaster copy. In FIG. 31, the first user instructs the first authoringapplication to instantiate the content updates into the document 2010displayed by the user interface 2000 of the first authoring application.Content changes made by the second user are now visible to the firstuser.

Embodiments of the disclosure may be implemented as a computer process(method), a computing system, or as an article of manufacture, such as acomputer program product or computer readable media. The processes(programs) can be implemented in any number of ways, including thestructures described in this document. One such way is by machineoperations, of devices of the type described in this document. Anotheroptional way is for one or more of the individual operations of themethods to be performed on a computing device in conjunction with one ormore human operators performing some of the operations. These humanoperators need not be collocated with each other, but each can be onlywith a machine that performs a portion of the program.

The computer program product may be a computer storage media readable bya computer system and encoding a computer program of instructions forexecuting a computer process. The computer program product may also be apropagated signal on a carrier readable by a computing system andencoding a computer program of instructions for executing a computerprocess. The term computer readable media as used herein includes bothstorage media and communication media.

Those skilled in the art will appreciate that the disclosure may bepracticed with other computer system configurations, including hand-helddevices, multiprocessor systems, microprocessor-based or programmableconsumer electronics, minicomputers, mainframe computers, and the like.The disclosure may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network. In a distributed computingenvironment, program modules may be located in both local and remotememory storage devices. Generally, program modules include routines,programs, components, data structures, and other types of structuresthat perform particular tasks or implement particular abstract datatypes.

What is claimed is:
 1. A method for collaborative authoring of adocument at a first computing device, the method comprising: allowingthe document to be viewed and edited by a first user on the firstcomputing device within a collaborative authoring environment; sending afirst update from the first computing device to the second computingdevice indicating that the first user is editing the document at a firstlocation; receiving a second update from the second computing device atthe first computing device indicating that a second user is editing thedocument at a second location; automatically applying the second updateto the document on the first computing device; and automaticallyproviding, by the first computing device, a first annotation identifyinga name of the second user displayed on the document at the secondlocation, wherein the first annotation indicates that the document isbeing edited by the second user at the second location.
 2. The method ofclaim 1, further comprising: locking at least a portion of the documentwhen the document is being edited by the first user.
 3. The method ofclaim 1, further comprising: locking at least a portion of the documentwhen the document is being edited by the second user.
 4. The method ofclaim 1, wherein a master copy of the document is stored at the secondcomputing device.
 5. The method of claim 1, further comprisingidentifying the second user by color.
 6. The method of claim 1, whereinthe second computing device is a storage device.
 7. The method of claim6, wherein the storage device is a server computing device.
 8. Themethod of claim 1, wherein the second update comprises one of: anaddition, a deletion, and a revision to content of the document.
 9. Themethod of claim 1, further comprising: receiving a third update from thesecond computing device at the first computing device indicating that athird user is editing the document at a third location; automaticallyapplying the third update to the document on the first computing device;and at the first computing device, providing a second annotationidentifying a name of the third user displayed on the document at thethird location indicating that the document is being edited by the thirduser at the third location.
 10. The method of claim 9, furthercomprising identifying the second user by a first color and identifyingthe third user by a second color, wherein the first color is differentthan the second color.
 11. A first computing device comprising: aprocessor; and a memory communicatively coupled to the processor, thememory storing computer-readable instructions that when executed by theprocessor cause the first computing device to: receive and display editsfrom a first user to a document displayed at the first computing device;concurrently receive an update from a second computing device, whereinthe update includes one or more edits to a first unit of data of thedocument displayed at the first computing device; automatically applythe update to the document; and automatically provide an annotation fordisplay on the document at a location associated with the first unit ofdata, the annotation identifying a name of the second user to indicateediting of the first unit of data by the second user.
 12. The firstcomputing device of claim 11, the computer-readable instructions furthercausing the first computing device to identify the second user by acolor.
 13. The first computing device of claim 11, wherein the secondcomputing device is a storage device.
 14. The first computing device ofclaim 11, the computer-readable instructions further causing the firstcomputing device to: receive one or more edits to a second unit of dataof the document from the first user; and lock the second unit of datawhen the one or more edits are received from the first user.
 15. Thefirst computing device of claim 11, the computer-readable instructionsfurther causing the first computing device to: lock the first unit ofdata when the update is received from the second computing device. 16.The first computing device of claim 11, wherein a master copy of thedocument is stored at the second computing device.
 17. A first computingdevice comprising: a processing unit; and a memory storing instructionsthat when executed by the processing unit cause the first computingdevice to perform the steps of: receiving edits to a first portion of adocument from a first user in a collaborative authoring environment;sending a first update from the first computing device to a secondcomputing device to indicate editing of the first portion of thedocument by the first user; receiving a second update from the secondcomputing device at the first computing device indicating editing of asecond portion of the document by a second user; automatically applyingthe second update to the second portion of the document; andautomatically displaying, by the first computing device, an annotationon the document identifying a name of the second user at a locationassociated with the second portion of the document to indicate editingof the second portion of the document by the second user.
 18. The firstcomputing device of claim 17, wherein the first computing device isfurther caused to perform a step of: locking at least the first portionof the document when the edits are received at the first computingdevice.
 19. The first computing device of claim 17, wherein the firstcomputing device is further caused to perform a step of: locking atleast the second portion of the document while the second portion isbeing edited.
 20. The first computing device of claim 17, wherein amaster copy of the document is stored at the second computing device.21. The first computing device of claim 17, wherein the first computingdevice is further caused to perform the steps of: receiving a thirdupdate from the second computing device at the first computing deviceindicating editing of a third portion of the document by the seconduser; automatically applying the third update to the document on thefirst computing device; and moving the annotation displayed on thedocument from the location associated with the second portion of thedocument to a location associated with the third portion of the documentto indicate editing of the third portion of the document by the seconduser.